Hi All, Currently i am using SCOM 2007R2. I having SCOM DW space issue. When i checked it the Datawarehouse grooming is not working it seems. So i tried to execute it manually. When i tried to Execute the below command nothing is happening. exec StandardDatasetGroom '29F6502B-187C-405C-9D92-78A57F2CEF4F' I found above Dataset id using select * from standarddataset command. Kindly help me. Regards, SAndy

Hi Sandy, First of all, why do you think it's not working? Take a look at this tools http://blogs.technet.com/b/stefan_stranger/archive/2009/08/15/everything-you-wanted-to-know-about-opsmgr-data-warehouse-grooming-but-were-afraid-to-ask.aspx I am asking because the "When i tried to Execute the below command nothing is happening." makes me think your grooming is fine and this SP just have nothing to do... http://OpsMgr.ru/

Hi Alex, I configured my Event Groom to "30" days, but when i checked the Oldest event data is on "Jan month" where i have around 100 days old event data in my DW. So it clearly shows the grooming is not working in my DW. How can i make it working.

There are ways, but I don't think most people post the sql queries, you would have to probably open a case.Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

Hi, you can find a script and run a grooming once. But it would not solve your issue because you need to find WHY grooming is stopped and fix this. As it could be a complex task and a lot of different things could be involved it is definitely a work for a support engineer. http://OpsMgr.ru/

The first thing you should do if you suspect the grooming jobs are not running properly is check the event logs on the MS. If you don't see any errors, you can increase the logging debuglevel for the grooming jobs by running the following query: Update StandardDataSet Set DebugLevel = 3 Where DebugLevel != 3 select * from DebugMessage The last column in this table, OperationDurationms is the duration it took for the grooming job to complete. Look for any really high duration, it could mean the grooming job is timing out. Please check if there are continuous NULL values as that also means timeouts. Many a times the failure can arise when the standarddatabase maintenance dataset is not running correctly. This can happen when lot of data is there on staging tables and you can use this link for more details http://blogs.technet.com/b/sudheesn/archive/2009/07/28/getting-31552-exception-sqlexception-timeout-expired-very-frequently-in-scom-server.aspx For detail pls. refer to http://blogs.technet.com/b/sudheesn/archive/2010/08/03/gooming-in-scom.aspx Roger

Hi All, I followed above mentioned steps, but still no go. In RMS i received EVENT:31552 and refer to Timed out for all dataset. So what i need to do next. Kindly explain me.

The most common issues causing the 31552 events seen are: A sudden flood (or excessive sustained amounts) of data to the warehouse that is causing aggregations to fail moving forward. The Exchange 2010 MP is imported into an environment with lots of statechanges happening. Excessively large ManagedEntityProperty tables causing maintenance to fail because it cannot be parsed quickly enough in the time allotted. Too many tables joined in a view or query (>256 tables) when using SQL 2005 as the DB Engine SQL performance issues (typically disk I/O) Using SQL standard edition, you might see these randomly at night, during maintenance as online indexing is not supported using SQL standard edition. Messed up SQL permissions Too much data in the warehouse staging tables which was not processed due to an issue and is now too much to be processed at one time. Random 31552s caused my DBA maintenance, backup operations, etc.. Roger

Then how to resolve this issue. I have nearly 500GB data in DW. In event alone i have 100+ days data around 450GB data. How to delete those data from Event dataset. Kindly assist me in step by step process.